Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix the order of private members for linting. #5101

Merged
merged 1 commit into from
Oct 23, 2024

Conversation

dbatiste
Copy link
Contributor

This PR bumps eslint-config-brightspace to v1.2.0 so that private members defined with # are identified as private for linting. Otherwise, eslint will expect these private members to be sorted among the public properties and methods.

@dbatiste dbatiste requested a review from a team as a code owner October 23, 2024 22:45
Copy link
Contributor

Thanks for the PR! 🎉

We've deployed an automatic preview for this PR - you can see your changes here:

URL https://live.d2l.dev/prs/BrightspaceUI/core/pr-5101/

Note

The build needs to finish before your changes are deployed.
Changes to the PR will automatically update the instance.

Copy link
Contributor

@GZolla GZolla left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@dbatiste dbatiste merged commit 09be0e5 into main Oct 23, 2024
6 checks passed
@dbatiste dbatiste deleted the dbatiste/fix-private-member-order branch October 23, 2024 22:53
@@ -63,6 +61,8 @@ export const _LocalizeMixinBase = dedupeMixin(superclass => class LocalizeMixinB
this.requestUpdate('localize');
}

#updatedProperties = new Map();
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I do find defining the private properties down here a little weird. But that's the order we always had for them.

Copy link

🎉 This PR is included in version 3.62.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants